System and method for intelligent dynamic message addressing

ABSTRACT

A method for dynamically modifying the “from” address in SCCP-level address in an SS7 message. An inter-carrier vendor (ICV) or intermediary prearranges with a domestic carrier and an inter-network network (e.g., Teleglobe) to replace the ICV&#39;s predetermined static “from” SCCP-level address with a different “from” SCCP-level address. The different address might be selectively or dynamically employed based on an identity of a source wireless carrier, an identity of a destination wireless carrier, a directory number of a source mobile station, or a directory number o f a destination mobile station. The different address may also be used to indicate branding or the fact that a carrier has merged or has acquired another carrier.

This application claims the benefit of U.S. Provisional Application No.60/574,995, filed May 28, 2004, which is herein incorporated byreference in its entirety.

BACKGROUND

1. Field of the Invention

The present invention relates generally to telecommunications services.More particularly, the present invention relates to Dynamic MessageAddressing capabilities of an SS7 Subsystem in connection with ShortMessage Service (SMS) message routing, processing, and deliveryinfrastructure that enables mobile carriers to exchange text and datamessages across all carriers, across all wireless protocols, and aroundthe world.

The following acronyms are used throughout this description.

Term Meaning ANSI American National Standards Institute BIB BackwardIndicator Number BS Base Station BSN Backward Sequence Number CCITTConsultative Committee on International Telegraphy and Telephony CCSCommon Channel Signaling CDMA Code Division Multiple Access CMSDB CallManagement Services Database CRC Cyclic Redundancy Check DN DirectoryNumber DPC Destination Point Code E.164 ITU international telephonenumbering plan recommendation EIA Electronic Industry Association ESNElectronic Serial Number FCS Frame Check Sequence FIB Forward IndicatorBit FISU Fill-In Signal Unit FSN Forward Sequence Number GMSC GatewayMSC GSM Global System for Mobile Communication GT Global Title GTTGlobal Title Translation HLR Home Location Register ICV Inter-CarrierVendor IMSI International Mobile Station Identity IN IdentificationNumber IP Internet Protocol ISO International Standards OrganizationISUP ISDN User Part ITU International Telecommunication Union IWMSCInterworking MSC LI Length Indicator LSSU Link Status Signal Unit MAPMobile Application Part MDN Mobile Directory Number MIN MobileIdentification Number MO Mobile Originated MS Mobile Subscriber MSCMobile Switching Center MSISDN Mobile Station ISDN Number MSU MessageSignal Unit MT Mobile Terminated MTP Message Transfer Part NANP NorthAmerican Numbering Plan NPDB Number Portability Database

2. Background of the Invention

SS7 concerns itself with the signaling component of the initiation,management, and termination of telecommunication services, includingpoint-to-point telephone calls.

In a telephony context, “signaling” means the passing, from one point toanother, of information and instructions relevant to the setting up orsupervision of a telephone call.

To initiate a call, a telephone subscriber lifts the handset off itsrest, which, in American English, is commonly referred to ‘going offhook.’ This off-hook state is a signal to the central office or“exchange” to be ready to receive the number of the called subscriber.As soon as appropriate receiving equipment has been connected to theline, the exchange signals dial tone to the calling subscriber who thendials the wanted number. The subscriber, in due course, receives advicefrom the exchange about the status of the call, namely, a ringing signal(indicating that the wanted line is being rung), an engaged or busy tonesignal (indicating that the wanted line is already busy with anothercall), an equipment busy tone signal (indicating congestion somewherebetween the called exchanged and the calling line), or some otherspecialized tone, or pre-recorded message.

These are the signals and tones with which the telephone subscribersthemselves are concerned. Telephone signaling is however also concernedwith the signaling of information between exchanges. See, generally,Graham Langley, Telecommunications Primer (2^(nd) Edition), PitmanPublishing, London, 1986.

More specifically, SS7 is what runs public wireless and wirelinenetworks. It is the communications network for the communicationsnetwork, that includes both a suite of protocols as well as anarchitecture.

When a user picks up the telephone in a home, or one connected to, e.g.,a company's private branch exchange (PBX), the telephone connects to apredetermined local telephone exchange. The exchange then routes thecall using SS7 protocols over SS7 links. In seconds, SS7 can send a callaround the world through all kinds of equipment. In case, for example,where the person being called has moved to a different state in theUnited States, SS7 will find out where. If the intended recipient is outand has voice-mail, SS7 will route the call to the mailbox, wherever itmay be.

In addition, when one dials a mobile phone or sends a text message, theSS7 network finds out where in the world that mobile phone is and routesthe call there, making sure the appropriate charges are logged. SS7 canalso reroute a call when a mobile user roams into the domain of anotherswitching center, or cut off a call when a prepaid service runs out ofmoney.

In short, SS7 is a dedicated packet switching network that carriescommand and control information. It is separate and apart from thecircuit switching network of the Public Switched Telephone Network(PSTN) that carries actual telephone calls. In effect, SS7 is a private,back-channel facility through which the different elements within atelecommunications environment (e.g., telephone switches) may, as anexample:

-   -   Exchange critical information (such as SMS messages, call        routing data, etc.), or    -   Manage the allocation and de-allocation of system resources        (e.g., actual voice circuits) during the creation, utilization,        and destruction of telephone call delivery paths through the        PSTN.

As summarized on a website belonging to Cisco (San Jose, Calif.), in themid-1960s, the CCITT (now the ITU) developed a digital signalingstandard called Signaling System #6. SS6 was based on a packet-switched,proprietary data network. SS6 used 2.4 Kbps data links to send packetsof data to distant switches to request services. This was the first useof packet switching in the PSTN. SS6 packets consisted of 12 signalunits of 28 bits each placed into a data block.

SS7 began deployment in 1983, and gradually phased out SS6. It wasinitially used only in the interoffice network (from central office tocentral office), but has gradually expanded and is now deployed in localcentral offices as well. SS7 provides a global standard for call setup,routing, and control.

The first use of SS7 was not for call setup and teardown, but rather foraccessing databases. Toll free “800” numbers provided a problem forswitches in that they could no longer route based on area code. A second“real number” for each 800 number needed to be placed in a centralizeddatabase which multiple central offices could access.

An SS7 network consists of an interconnected set of elements orcomponents. The elements within an SS7 network are referred to asSignaling Points (SPs). Each SP is assigned its own unique Point Code(PC) that serves as an address within the SS7 network which other SPsmay employ when dispatching messages. An SS7 PC may be thought of asbeing similar to an Internet Protocol (IP) address on the Internet. PCsare carried within all of the messages that travel through an SS7network to identity the sender and the recipient of a message—the PC ofthe sender of a message is referred to as the Origination PC (OPC) andthe PC of the recipient of a message is referred to as the DestinationPC (DPC).

In the United States an American National Standards Institute (ANSI)version of SS7 is utilized and a PC is a 24-bit value that can beexpressed in the form:

-   -   N.C.M        where N is an 8-bit value that identifies a Network component        (and may contain a value in the range 0 . . . 255 [inclusive]),        C is an 8-bit value that identifies a Cluster component (and may        contain a value in the range 0 . . . 255 [inclusive]), and M is        an 8-identifies bit value that identifies a Member component        (and may contain a value in the range 0 . . . 255 [inclusive]).        Using this scheme, a total of 16,644,864 PCs are available for        assignment:

Network Usage 0 Not Used 1 Cluster values 1, . . . 255 assigned as‘quasi network’ codes to small entities 2 Cluster values 1, . . . 255assigned as ‘quasi network’ codes to small entities 3 Cluster values 1,. . . 255 assigned as ‘quasi network’ codes to small entities 4 Clustervalues 1, . . . 255 assigned as ‘quasi network’ codes to small entities5 Cluster values 1, . . . 255 and Member values (0, . . . 255) assignedas blocks to individual entities 6 Available for complete assignment . .. 254 Available for complete assignment 255 Reserved For Future Usewhere network values 1 through 5 contribute a total of 326,400 possiblevalues (5 Network values*255 Cluster values*256 Member values=326,400values) and network values 6 through 254 contribute a total of16,318,464 values (249 Network values*256 Cluster values*256 Membervalues=16,318,464 values).

As an example, the ANSI SS7 PC 2.16.3 could be represented in binary as00000010 00010000 00000011 or as the decimal value 135171.

In parts of Europe an International Telecommunication Union (ITU)version of SS7 is utilized and a PC is a 14-bit value that can beexpressed in the form:

-   -   Z.A.M        where Z is a 3-bit value that identifies a Zone component (and        may contain a value in the range 0 . . . 7 [inclusive]), A is an        8-bit value that identifies an Area or Network component (and        may contain a value in the range 0 . . . 255 [inclusive]), and M        is a 3-bit value that identifies a Member component (and may        contain a value in the range 0 . . . 7 [inclusive]).

As an example, the ITU SS7 PC 2.16.3 could be represented in binary as010 00010000 011 or as the decimal value 4227.

In other portions of the world, still other versions of SS7 areutilized, and as a consequence, the local PC size and PC structure isaltogether different—e.g., in Japan, PCs are 16-bit values.

There are three types of SS7 SPs: Service (or Signal) Switching Point(SSP), Service (or Signal) Control Point (SCP), and Signal TransferPoint (STP).

An SSP is basically an end-point within an SS7 environment and istypically some type of switching facility, for example a local exchangeor a central office. An SSP is connected to an STP by one or more SS7Access (A) Links. In topology diagrams, an SSP is typically depicted orrepresented using the symbol shown in FIG. 1.

An SCP typically comprises one or more database environments (e.g., aCall Management Services Database [CMSDB] for translating toll-freenumbers, a Number Portability Database [NPDB] for translating portednumbers, etc.) and the associated application software. Each of thedatabase environments that is hosted by an SCP is identified by a uniqueSubsystem Number (SSN). Thus one may address a message to a specificdatabase on a specific SCP using the combination of the SCP's PC and theappropriate SSN. The combination of an SCP PC and an SSN may be thoughtof as being functionally analogous to the combination of an IP addressand a port number—i.e., the combination uniquely identifies a specificend-point entity. An SCP is connected to an STP by one or more SS7Access (A) Links. In topology diagrams, an SCP is typically depicted orrepresented using the symbol shown in FIG. 2.

An STP is, principally, a router, accepting incoming messages andimmediately dispatching them to their designated destination PC. Thereare different classes or levels of STPs, including the National STP(which is capable of routing messages only to other SPs that understandits specific version [ANSI, ITU, etc.] of SS7) and the Gateway orInternational STP (which is capable of performing the necessaryconversion operations to bridge the protocol ‘gap’ between differentversions of SS7). As described above, ANSI and ITU PCs are quitedifferent and one of the fundamental services that a Gateway orInternational STP offers is PC mapping and conversion. Additionally, anSTP may optionally support Global Title Translation (GTT), a facilitythrough which the address (i.e., a PC and a SSN) of the appropriatetarget SCP is dynamically derived from data tables that are storedlocally on the STP and a Global Title (GT), an alias value (e.g., amobile telephone number, a toll-free telephone number, etc.) that iscontained in an incoming message. STPs are always deployed in matedpairs. An STP is connected to its mate by a set of SS7 Cross (C) links.A set of mated STPs are connected to another set of mated STPs by a setof SS7 Bridge (B) links. In topology diagrams, an STP is typicallydepicted or represented using the symbol shown in FIG. 3.

FIG. 4 illustrates a hypothetical (albeit exceedingly simple) ANSI SS7network. In this diagram, two pairs of mated STPs (at PCs 1.1.8/1.1.9and 2.1.8/2.1.9) support eight SSPs (at PCs 1.1.2, 1.1.3, 1.1.4, 1.1.5,2.1.2, 2.1.3, 2.1.4, and 2.1.5) and two SCPs (at PCs 1.1.1 and 2.1.1).Message delivery routes would be defined between all of the differentSPs (e.g., a message delivery route exists from the SP at PC 1.1.2 tothe SP at PC 1.1.8, a message delivery route exists from the SP at PC1.1.2 to the SP at PC 1.1.9, etc.), published, and for managementpurposes aggregated into routesets. Utilizing the published oradvertised message delivery paths, the SPs within the network are thusable to properly direct all of the messages that must be exchangedbetween the SPs.

A four-level SS7 protocol stack that follows the layering concept of theOpen Systems Interconnection (OSI) seven-layer reference model asdefined by the International Standards Organization (ISO) supports theexchange of messages between SPs within an SS7 environment. Withreference to FIG. 5, the Message Transfer Part (MTP) levels 1, 2, and 3define various low-level messaging support (e.g., physical connections,message sequencing, error detection, message routing, etc.). TheSignaling Connection Control Part (SCCP) provides connection-orientedand connectionless services and GTT. The Transaction CapabilitiesApplications Part (TCAP) supports the exchange of application-specificmessages (e.g., a database query issued to and a response returned froman SCP). There are three distinct types of messages or Signal Units(SUs) that transit an SS7 environment—Fill-In Signal Units (FISUs), LinkStatus Signal Units (LSSUs), and Message Signal Units (MSUs). FISUs andLISUs convey heartbeat and other status information. MSUs are the realworkhorse of SS7 and convey all of the call control information,database query and response information, SMS messages, etc. An MSU maybe depicted as shown in FIG. 6.

The Frame Check Sequence (FCS) FCS contains a Cyclic Redundancy Check(CRC) value that is utilized to detect and, if possible, correct messagetransmission errors. The Signaling Information Field (SIF) containshigher-level (e.g., SCCP, TCAP, etc.) signaling information and aRouting Label (RL) comprising the OPC and DPC of the message. TheService Information Octet (SIO) identifies the nature of the MSU and thehigher-level (e.g., SCCP, TCAP, etc.) ‘user’ to which the contents ofthe SIF should be delivered for decoding and processing. The LengthIndicator (LI) identifies the type of the SU. The contents of theForward Indicator Bit (FIB), Forward Sequence Number (FSN), BackwardIndicator Bit (BIB), and Backward Sequence Number (BSN) are utilized forsequencing, acknowledgement, and error recovery purposes. The Flag fieldcontains the static value 01111110 and identifies the end of a MSU.

The SIF is effectively the payload of the MSU. It carries thehigher-level (e.g., SCCP, ISUP, etc.) signaling information andcontains, amongst other fields, the RL. An RL identifies principally thePC of the SP that originated the MSU (i.e., the OPC) and the PC of theintended recipient SP of the MSU (i.e., the DPC).

With this basic understanding of SS7 now established, briefly describednext is SMS and the utilization of SS7 within an SMS infrastructure.

Publications from various of the worldwide authoritative bodies describethe organization and operation of wireless telecommunicationsenvironments and services or features within those environments such asSMS. For example, for the Global System for Mobile communication (GSM)environment the Technical Specifications (TSs) are maintained by the3^(rd) Generation Partnership Project (http://www.3gpp.org), andnumerous volumes are available in the popular press (including, amongstothers, Michel Mouly and Marie-Bernadette Pautet, The GSM System ForMobile Communications, Europe Media Duplication S.A., 1993).

Within a (hypothetical) wireless telecommunications environment likethat shown in FIG. 7, one typically has some number of MobileSubscribers (MSs) 70. An example of a MS 70 would be a cellulartelephone, which in effect is a portable radio transmitter/receiver. AnMS is assigned (at least) two identifying values—a public DirectoryNumber (DN) (the advertised telephone number, typically E.164-compliant,that individuals may dial to reach the MS) and a private IdentificationNumber (IN) (a behind-the-scenes number that is utilized during callprocessing, routing, etc. operations). Depending upon the MS′ technology(GSM, non-GSM such as Code Division Multiple Access [CDMA]) the DN andthe IN are ascribed the following designations:

Technology Value Designation Description GSM DN MSISDN Mobile StationISDN IN IMSI International Mobile Subscriber Identity Non-GSM DN MDNMobile Directory Number IN MIN Mobile Identification Number

A MS communicates with a Base Station (BS), each of which consists of aradio antenna and supporting systems. The coverage area that a BSsupplies is commonly referred to as a ‘cell,’ several of which areidentified by 72 a-72 d. By strategically distributing BSs a wirelesstelecommunications service provider can ‘join together’ a group of cellsto provide coverage for incrementally larger contiguous areas. One ormore BSs are connected by land lines to a Mobile Switching Center (MSC)73, a specialized telephone switch that serves as an entry/exit pointfor:

-   -   The carrier's SS7 environment 75    -   The PSTN 76        thus facilitating the passing of traffic between the wireless        environment and the wireline environment.

As a MS 70 roams (i.e., as it moves from one coverage area to another)the wireless telecommunications service provider's back-end systems (HLR78 and VLR 79) automatically keep track of the location of the MS—sothat calls that are originated from the MS 70 may be efficientlyprocessed and calls that are terminated to the MS 70 may be properlydelivered—through a carefully choreographed exchange of SS7 messages. Tosupport this ‘mobility management’ capability critical information ismaintained in two different database environments:

-   -   1) Home Location Register (HLR) 78. At a logical level there is        one HLR 78 within each carrier's environment; at a physical        level this facility may be implemented as a series of        interconnected database environments. When a carrier activates        service for a MS 70 an entry is made in this database. The        database entry captures, for example, the MS′ hidden Electronic        Serial Number (ESN), the MS′ Identification Number (the private        number that is utilized behind the scenes during actual call        processing and routing operations), the MS′ DN (the public        telephone number that individuals may dial to reach the MS), the        identifier of the VLR for the current location of the MS (so        that calls may be delivered to the MS), etc.    -   2) Visitor Location Register (VLR) 79. As a MS 70 roams a        temporary entry is created in the VLR in the MSC that services        the cell (i.e., the BS or cell 72 a-72 d) within which the MS 70        currently resides. Amongst other things, the database entry        captures the temporary DN that is assigned to the MS 70 for        purposes of call processing for the period of time that the MS        is active in the cell.

The various specification documents that define SMS identify several new(SMS-specific) network elements, as is well known in the art. In brief,at a very high level, and in stylized form, those network elements maybe summarized as shown in FIG. 8.

One or more Short Message Entities (SMEs) 80 a, 80 b, 80 c send SMSmessages to and receive SMS messages from a Short Message Service Center(SMSC or sometimes SC) 82. The SMSC is responsible for, amongst otherthings, relaying and, if necessary, temporarily storing SMS messages.

An SMS Gateway MSC (SMS-GMSC) 84 capability, possibly offered as aservice by a suitably-equipped MSC, accepts SMS messages from a SMSC 82,appropriately interrogates HLR 78 to obtain routing information, andpasses SMS messages on to the identified MSC 73.

An SMS Interworking MSC (SMS-IWMSC) 86 capability, possibly offered as aservice by a suitably-equipped MSC, receives SMS messages from a MSC 73and submits SMS messages to the identified SMSC 82.

As noted previously, the coordinated exchange of a series ofwell-structured SS7 messages is necessary to support the roaming of a MS70. For example, such messaging is necessary to support the registrationof a MS 70 within a new VLR 79, the updating of the ‘current VLR’ fieldof a MS′ record in the HLR, the deregistration of a MS within an oldVLR, etc. In CDMA-based wireless environments the TIA/EIA 41 (or IS-41Dor ANSI-41D) Mobile Application Part (MAP) extensions to SS7 aretypically utilized for this activity; in GSM wireless environments theGSM MAP extensions to SS7 are typically utilized for this activity. TheTIA/EIA 41 MAP extensions and the GSM MAP extensions sit atop the TCAPlayer of the SS7 protocol stack.

Thus, SS7 can be considered the ‘glue’ that ties together all of thepieces of the puzzle. By leveraging features of SS7, the presentinvention provides a methodology by which an inter-carrier vendor cancustomize certain messaging processes.

SUMMARY OF THE INVENTION

In accordance with the present invention, an inter-carrier vendor, orIntermediary, that routes, e.g., short message service (SMS) messages,is able to dynamically (a) identify and then (b) assign a “from”SCCP-level address of outgoing SS7 messages (associated with SMSmessages) that it dispatches based on (a) the application of a definedset of rules or logic (which is dynamically configurable on acarrier-specific basis) and (b) the value of one or more data elements(the precise set of which are dynamically configurable on acarrier-specific basis). The Intermediary preferably works in acoordinated fashion with an international carrier, such as Teleglobe, toensure that responses (by, for example, another international carrier)to dynamically-addressed SS7 messages that are issued by theIntermediary are properly routed (via, for example, GTT operationswithin Teleglobe) back to the Intermediary.

The Intermediary can thus employ a selected “from” SCCP-level address tomore readily identify, e.g., the identity of a source wireless carrier,the identify of a destination wireless carrier, a directory number of asource or destination mobile station. This identification can be helpfulfor improved billing services, accounting, and branding of messages.

In an alternative embodiment, a “from” SCCP-level address is selectedfrom a pool of such address depending on a particular rules set orpredetermined logic and associated data.

These and other features of the present invention will be more readilyappreciated upon a reading of the following detailed description inconjunction with the associated drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1-3 depict schematic symbols of basic public switched telephonenetwork components employed in an ANSI SS7 network.

FIG. 4 illustrates a hypothetical ANSI SS7 network.

FIG. 5 juxtaposes IP, OSI and SS7 reference layers.

FIG. 6 shows a conventional SS7 Message Signal Unit (MSU).

FIG. 7 shows a conventional wireless telephone network.

FIG. 8 shows a conventional SMS network architecture.

FIG. 9 shows the delivery of an SMS message to a mobile station.

FIG. 10 shows the delivery of an SMS message from a mobile station.

FIG. 11 depicts a framework for converting between domestic andinternational numbers.

FIGS. 12 and 13 illustrate the processing of a message.

FIG. 14 shows a “from” SCCP-level address that can be dynamicallychanged in accordance with the present invention.

DETAILED DESCRIPTION

To provide a substantive context for the present invention, consider fora moment the following illustrative example—the delivery of an SMSmessage to a MS (i.e., a Mobile Terminated [MT] message). The messageflow that is associated with this activity may be summarized in thediagram of FIG. 9.

At Step 901, an SME 80 delivers an SMS message to the SMSC 82. The SMSmessage contains, amongst other things, the MSISDN of the recipient MS(MS _(a)) 70.

At Step 902, the SMSC 82 forwards the SMS message on to an SMS-GMSC 84.

At Step 903, the SMS-GMSC 84 issues a MAP_SEND_ROUTING_INFO_FOR_SM (SRIFor SM) to the HLR 78. The HLR 78 utilizes the MSISDN value in theMAP_SEND_ROUTING_INFO_FOR_SM message to retrieve the associated IMSIvalue and the address of the MSC that is currently servicing the MS 70.

At Step 904, a MAP_SEND_ROUTING_INFO_FOR_SM_ACK (SRIForSM_ACK)containing the retrieved information (the IMSI, the address of theservicing MSC, etc.) is returned to the SMS-GMSC 84.

At Step 905, the SMS-GMSC 84 transfers the SMS message to the MSC 73that is currently servicing the recipient MS 70 by utilizing thereturned routing address to issue a MAP_FORWARD_SHORT_MESSAGE (FSM) withthe MS destination address set to the IMSI to the MSC.

At Step 906 and Step 907, the servicing MSC 73 issues aMAP_SEND_INFO_FOR_MT_SMS to the VLR to retrieve location, etc.information for the MS.

At Step 908, the MSC 73 actually dispatches the SMS message to therecipient MS (MS _(a)) 70.

Now consider the reverse case—the issuance of an SMS message by a MS 70(i.e., a Mobile Originated [MO] message). The message flow that isassociated with this activity may be summarized in the diagram of FIG.10.

At Step 1001, the originating MS (MS _(a)) 70 issues an SMS message.

At Step 1002 and Step 1003, the servicing MSC 73 issues aMAP_SEND_INFO_FOR_MO_SMS to the VLR 79 to retrieve identification,location, and routing information for the MS.

At Step 1004, the servicing MSC 73 transfers the SMS message to theSMS-IWMSC 84 by utilizing local routing guides and the information aboutthe MS that was retrieved previously from the VLR 79 to issue aMAP_FORWARD_SHORT_MESSAGE(FSM).

At Step 1005, the SMS-IWMSC 84 forwards the SMS message on to a SMSC 82.

At Step 1006, the SMSC 82 delivers the SMS message to the recipient SME80.

To further explore aspects of the two sequences that were just presentedwe may utilize the framework depicted in FIG. 11.

Within this framework Teleglobe (a description of which can be found onthe internet at “teleglobe.com”) is indicated as an SS7 access andservice provider. Teleglobe can be considered an inter-network network,in the sense that it provides connectivity between different stand-alonenetworks. It will be readily obvious to one of ordinary skill in therelevant art that other such providers may easily be substituted.

Additionally, an Intermediary is indicated as an Inter-Carrier Vendor(ICV) servicing some number of domestic wireless carriers. Anillustrative example of key aspects of such an environment may be foundin pending U.S. application Ser. No. 10/426,662.

It is noted that, for clarity, the various telephone numbers that aredepicted are shown with embedded dashes (‘-’). Additionally, please notethat for added clarity certain data elements for selected of themessages are ‘carried over’ through the invocation→response messagingsequence. Also, in selected cases various of the logical GMSC, HLR,SMSC, etc. functionality is ‘collapsed’ under a single XXX designation.Finally, in certain cases and for simplicity, a final GTT operation isdepicted when in reality an intermediate GTT operation is more likely tobe encountered.

Consider the case where a MS, MS_(b) 71, of a domestic carrier that isserviced by the Intermediary 1100 originates a SMS message that isaddressed to (i.e., is destined for) MS_(a) 70, a MS of an internationalcarrier. MS_(a) 70 has the DN 65-9850-2799 and MS_(b) 72 has the DN1-301-5551212.

FIG. 12 summarizes, at a very high level, the processing of themessaging that arises under this case. In brief:

At Step 1201, an Intermediary SS7 Transmitter process constructs anIP-side SendRoutingInfoForSM (SRIForSM) message and submits that messageto the IP side of the Intermediary's SS7 gateway platform.

At Step 1202, the Intermeidary's SS7 gateway platform, which resides atPC 001-044-246 and E.164 node address 1-703-9618308, constructs aSendRoutingInfoForSM (SRIForSM) request message and issues that messageto Teleglobe's ANSI facing access point (at PC 001-044-230).

At Step 1203, Teleglobe completes the necessary message conversions(ANSI to ITU) and performs a GTT operation (for simplicity, illustratedhere as a final GTT operation). The GTT operation ‘maps’ the DN of therecipient or destination MS (i.e., 65-9850-2799) to the PC 1.234.6.

At Step 1204, Teleglobe issues a converted and properly-addressedSendRoutingInfoForSM (SRIForSM) request message.

At Step 1205, after processing the SendRoutingInfoForSM (SRIForSM)request message a SendRoutingInfoForSM (SRIForSM) acknowledgement orresponse message is issued to Teleglobe's ITU facing access point (at PC2.321.6).

At Step 1206, Teleglobe completes the necessary message conversions (ITUto ANSI) and performs a final GTT operation. The GTT operation ‘maps’the E.164 address of the Intermediary's SS7 gateway platform (i.e.,1-703-9618308) to the PC 001-044-246, the PC of the Intermeidary's SS7gateway platform.

At Step 1207, Teleglobe issues a converted and properly-addressedSendRoutingInfoForSM (SRIForSM) acknowledgement/response message to theIntermediary's SS7 gateway platform.

At Step 1208, the Intermediary's SS7 gateway platform receives theSendRoutingInfoForSM (SRIForSM) acknowledgement/response message on itsSS7 side, constructs an IP-side SendRoutingInfoForSM (SRIForSM)acknowledgement/response message, and issues that message out its IPside for handling by an associated SMS message routing, processing, anddelivery infrastructure (no shown).

Following the successful completion of the preparatorySendRoutingInfoForSM (SRIForSM), Intermediary 1100 utilizes dataelements from the received SendRoutingInfoForSM(SRIForSM)acknowledgement/response message to construct and dispatch aForwardShortMessage (FSM) message to actually convey the SMS messageitself. The diagram that is presented in FIG. 13 summarizes, at a veryhigh level, the processing of the messaging.

At Step 1301, the Intermediary's SS7 Transmitter process constructs anIP-side ForwardShortMessage (FSM) message and submits that message tothe IP side of the SS7 gateway platform.

As Step 1302, the Intermediary's SS7 gateway platform, which resides atPC 001-044-246 and E.164 node address 1-703-9618308, constructs aForwardShortMessage (FSM) request message and issues that message toTeleglobe's ANSI facing access point (at PC 001-044-230).

At Step 1303, Teleglobe completes the necessary message conversions(ANSI to ITU) and performs a GTT operation (for simplicity, illustratedhere as a final GTT operation). The GTT operation ‘maps’ the destinationaddress (i.e., 65-9100-7780) to the PC 1.234.8.

At step 1304, Teleglobe issues a converted and properly-addressedForwardShortMessage (FSM) request message.

At Step 1305, after processing the ForwardShortMessage (FSM) requestmessage, a ForwardShortMessage (FSM) acknowledgement/response message isissued to Teleglobe's ITU facing access point (at PC 2.321.6).

As Step 1306, Teleglobe completes the necessary message conversions (ITUto ANSI) and performs a final GTT operation. The GTT operation ‘maps’the E.164 address of InphoMatch's SS7 gateway platform (i.e.,1-703-9618308) to the PC 001-044-246, the PC of the Intermediary's SS7gateway platform.

At Step 1307 Teleglobe issues a converted and properly-addressedForwardShortMessage (FSM) acknowledgement/response message to theIntermediary's SS7 gateway platform.

At Step 1308, the Intermediary's SS7 gateway platform receives theForwardShortMessage (FSM) acknowledgement/response message on its SS7side, constructs an IP-side ForwardShortMessage (FSM)acknowledgement/response message, and issues that message out its IPside for handling by SMS message routing, processing, and deliveryinfrastructure (not shown) of Intermediary 100.

With the foregoing in mind, details of the present invention can now bemore fully described.

Referring back to Step 1202 of FIG. 12 and Step 1302 of FIG. 13, one mayobserve that the SS7 messages that are dispatched by the Intermediary's1100 SS7 gateway platform—SendRoutingInfoForSM (SRIForSM) under FIG. 12and ForwardShortMessage (FSM) under FIG. 13—contain a static ‘from’SCCP-level address (1-703-9618308), as shown in FIG. 14.

While this is functional, it may be desirable for Intermediary 1100,operating as an ICV, and thus providing a ‘facade’ behind which numerousdomestic wireless carriers may reside, to optionally vary the ‘from’SCCP-level address of the SS7 messages that it issues. Specifically, itmay be desirable for Intermediary 1100, operating as an ICV, tooptionally dynamically populate the ‘from’ SCCP-level address of anoutgoing SS7 message that it dispatches based on (a) a dynamicallyconfigurable range of data elements (including, for example, theidentity of the source wireless carrier, the identity of the destinationwireless carrier, the DN of the source MS, etc.) and (b) a dynamicallyconfigurable body of application logic (that operates on or against, forexample, the pool of data elements).

It is noted that the catalog of data elements that was presented aboveis illustrative only; it will be readily apparent to one of ordinaryskill in the relevant art that numerous other data elements are easilypossible.

The motivation for such a dynamic message addressing capability mayinclude wireless carrier-specific business drivers (e.g., brandinginitiatives, MS management needs following a merger or acquisition,corporate privacy concerns, logical messaging segmentation, etc.) andICV-specific initiatives (e.g., augmented or enhanced billing offerings,etc.).

A Dynamic Message Addressing component of the SS7 Subsystem of theIntermediary provides the capability just described. Working in acoordinated fashion with Teleglobe (as the instant SS7 access andservice provider, although other such access/service entities may easilybe substituted) Intermediary 1100 is able to dynamically (a) identifyand then (b) assign the ‘from’ SCCP-level address of outgoing SS7messages that it dispatches based on (a) the application of a definedset of rules or logic (which is dynamically configurable on acarrier-specific basis) and (b) the value of one or more data elements(the precise set of which are dynamically configurable on acarrier-specific basis). The ‘working in a coordinated fashion withTeleglobe’ element is significant, as Teleglobe's routing databases mustbe kept in synchronization with the Intermediary's routing databases toensure that responses (by, for example, an international carrier) todynamically-addressed SS7 messages that are issued by Intermediary 1100are properly routed (via, for example, GTT operations within Teleglobe)back to Intermediary 1100.

For purposes of illustration consider the following simple hypotheticalexample. Under this example a domestic wireless carrier that is servicedby Intermediary 1100 (in its role as ICV) wishes to ensure that anyoutgoing SS7 messages that are dispatched by Intermediary 1100 on behalfof the carrier (e.g., during the completion of a message exchangeoperation in support of a MS of the carrier) ‘appear’ to originate froma single network element within the wireless carrier and not, as wouldnormally be the case, to originate from a single network element withinIntermediary 1100 (as disclosed through the static ‘from’ SCCP-leveladdress).

More specifically, the domestic wireless carrier would supply toIntermediary 1100 an E.164 address A₁ that the carrier wishes to be usedas a ‘from’ SCCP-level address. The address would presumably beassociated with the carrier through, for example, NPA-NXX or NPA-NXX-Xassignment under the rules of the North American Numbering Plan (NANP).

Intermediary 1100 would supply the E.164 address to Teleglobe'sprovisioning group for Teleglobe to apply to their systems. Upon thecompletion of Teleglobe's provisioning steps, the E.164 address would(e.g., through GTT) be associated with the SS7 Point Code of theIntermediary's SS7 gateway platform.

Intermediary 1100 also preferably alters the configuration of its SS7gateway platform to (a) recognize the E.164 address as being availablefor use and (b) associate the E.164 address to the supplying carrier.

Intermediary 1100 also preferably alters a rules set associated with itsSS7 gateway platform to indicate replacement of the static value1-703-9618308 with the carrier-supplied value A₁ in the ‘from’SCCP-level address of all outgoing SS7 messages for the instant carrier.Note that this replacement applies only to those outgoing SS7 messagesfor the instant carrier; all other outgoing SS7 messages retain use ofthe static value 1-703-9618308.

Under an alternative example, a domestic wireless carrier that isserviced by Intermediary 1100 (in its role as ICV) wishes to have anyoutgoing SS7 messages that are dispatched by Intermediary 1100 on behalfof the carrier (e.g., during the completion of a message exchangeoperation in support of a MS of the carrier) ‘appear’ to originate fromone of several virtual network elements within the wireless carrier andnot, as would normally be the case, to originate from a single networkelement within Intermediary 1100 (again, as disclosed through the static‘from’ SCCP-level address).

In this case, the domestic wireless carrier would supply to Intermediary1100 (a) one or more E.164 addresses A₁, A₂, . . . A_(n) that thecarrier wishes to be used as ‘from’ SCCP-level addresses and (b) therules or logic that fully and completely proscribe the use of thoseaddresses (e.g., when the first address A₁ is to be employed, when thesecond address A₂ is to be employed, etc.). The addresses wouldpresumably be associated with the carrier through, for example, NPA-NXXor NPA-NXX-X assignment under the rules of the NANP.

Intermediary 1100 would supply the E.164 addresses to Teleglobe'sprovisioning group for Teleglobe to apply to their systems. Upon thecompletion of Teleglobe's provisioning steps, the E.164 addresses would(e.g., through GTT) be associated with the SS7 Point Code of theIntermediary's SS7 gateway platform.

Intermediary 1100 preferably alters the configuration of its SS7 gatewayplatform to (a) recognize the E.164 addresses as being available for useand (b) associate the E.164 addresses to the supplying carrier.

Intermediary 1100 preferably also alters a rules set for its SS7 gatewayplatform to include the carrier-supplied rules or logic that fully andcompletely proscribe the use of the replacement addresses—e.g., when thefirst address is to be employed, when the second address is to beemployed, etc. Note that this replacement applies only to those outgoingSS7 messages for the instant carrier; all other outgoing SS7 messagesretain use of the static value 1-703-9618308.

It will be readily apparent to one of ordinary skill in the relevant artthat many other examples are easily possible.

While the narrative that was just presented concerned SMS, it will bereadily obvious to one of ordinary skill in the relevant art that otheruses of the Dynamic Message Addressing capability are easily possible.In fact, precisely because of the ubiquitous use of SS7 bytelecommunications providers many alternatives are, in fact, easilypossible.

The foregoing disclosure of the preferred embodiments of the presentinvention has been presented for purposes of illustration anddescription. It is not intended to be exhaustive or to limit theinvention to the precise forms disclosed. Many variations andmodifications of the embodiments described herein will be apparent toone of ordinary skill in the art in light of the above disclosure. Thescope of the invention is to be defined only by the claims appendedhereto, and by their equivalents.

Further, in describing representative embodiments of the presentinvention, the specification may have presented the method and/orprocess of the present invention as a particular sequence of steps.However, to the extent that the method or process does not rely on theparticular order of steps set forth herein, the method or process shouldnot be limited to the particular sequence of steps described. As one ofordinary skill in the art would appreciate, other sequences of steps maybe possible. Therefore, the particular order of the steps set forth inthe specification should not be construed as limitations on the claims.In addition, the claims directed to the method and/or process of thepresent invention should not be limited to the performance of theirsteps in the order written, and one skilled in the art can readilyappreciate that the sequences may be varied and still remain within thespirit and scope of the present invention.

1. A method of operating an inter-carrier vendor having an assignedE.164 address and that is configured to route messages using SS7signaling using the assigned E.164 address, the method comprising thesteps of: at an inter-carrier vendor, receiving from a domestic carrieran E.164 address to be used as a “from” SCCP-level address instead of astatic E.164 address assigned to the inter-carrier vendor; providing thereceived E.164 address to an inter-network network so that the receivedE.164 address is thereafter associated with the inter-carrier vendor;associating the received E.164 address with the domestic carrier withinthe inter-carrier vendor; and for subsequent outgoing SS7 messages beingrouted on behalf of the domestic carrier, replacing the static E.164address with the received E.164 address as the “from” SCCP-leveladdress.
 2. The method of claim 1, wherein the step of replacing ispreformed in accordance with a predefined rules set or logic.
 3. Themethod of claim 2, wherein the rules set is dynamically configurable. 4.The method of claim 2, wherein the step of replacing further comprisesanalyzing a data element in conjunction with the rules set.
 5. Themethod of claim 4, wherein the data element comprises at least one of anidentity of a source wireless carrier, an identity of a destinationwireless carrier, a directory number of a source mobile station, and adirectory number of a destination mobile station.
 6. The method of claim1, wherein the received E.164 address is indicative of a brand.
 7. Themethod of claim 1, wherein the received E.164 address is used in thecontext of a wireless carrier merger or acquisition.
 8. The method ofclaim 1, wherein the received E.164 is employed to account for augmentedor enhanced billing offerings.
 9. The method of claim 1, furthercomprising receiving a plurality of E.164 addresses from the domesticcarrier.
 10. The method of claim 9, wherein one of the plurality ofE.164 addresses is selected to be used as the “from” SCCP-level addressfor outgoing SS7 messages in accordance with the rules set or logic. 11.In a process of routing a short message service (SMS) message through aninter-carrier vendor, a method of dynamically employing a “from”SCCP-level address in an outgoing SS7 message, comprising the steps of:coordinating with a domestic carrier to receive an E.164 address to beused as a “from” SCCP-level address instead of a static E.164 addressthat would otherwise be used by an inter-carrier vendor in sending SS7messages; coordinating with an inter-network network to ensure that theE.164 address received from the domestic carrier is mapped to theinter-carrier vendor; associating the received E.164 address with thedomestic carrier within the inter-carrier vendor; and for subsequentoutgoing SS7 messages being routed by the inter-carrier vendor on behalfof the domestic carrier, replacing the E.164 address that wouldotherwise be used by the inter-carrier vendor with the E.164 addressreceived from the domestic carrier as the “from” SCCP-level address. 12.The method of claim 11, wherein the step of replacing is preformed inaccordance with a predefined rules set or logic.
 13. The method of claim12, wherein the rules set is dynamically configurable.
 14. The method ofclaim 12, wherein the step of replacing further comprises analyzing adata element in conjunction with the rules set.
 15. The method of claim14, wherein the data element comprises at least one of an identity of asource wireless carrier, an identity of a destination wireless carrier,a directory number of a source mobile station, and a directory number ofa destination mobile station.
 16. The method of claim 11, wherein theE.164 address received from the domestic carrier is indicative of abrand.
 17. The method of claim 11, wherein the E.164 address receivedfrom the domestic carrier is used in the context of a wireless carriermerger or acquisition.
 18. The method of claim 11, wherein the E.164address received from the domestic carrier is employed to account foraugmented or enhanced billing offerings.
 19. The method of claim 11,further comprising receiving a plurality of E.164 addresses from thedomestic carrier.
 20. The method of claim 19, wherein one of theplurality of E.164 addresses is selected to be used as the “from”SCCP-level address for outgoing SS7 messages in accordance with therules set or logic.